docs: refresh the README for 1.1.0, and give the product its own mark - #80
Merged
Conversation
`.gitignore` excludes `docs/*` and re-admits named entries, and `docs/images/` was never among them. The images the README already rendered were tracked from before that rule, so nothing looked wrong — but every new file added under `docs/images/` was invisible to git and would have reached `main` as a broken image link. Re-admit the directory alongside `docs/specs/`.
The README still described the app as of 1.0.1. Nothing from 1.1.0 was in it, and its header carried the Bitwize wordmark under `alt="Logue"` — the product had no mark of its own on the page at all. Header. A single composite banner: Bitwize.ai at the left edge, the Logue wordmark at the right, with a `<picture>` swap to white silhouettes on dark. The obvious markup for this does not work — GitHub's stylesheet sets `display: block; width: max-content` on markdown tables, which overrides `width="100%"` and collapses percentage-width cells onto the left. Compositing puts the justification in the image's own geometry, so it holds at every viewport and renders the same outside GitHub. The banner is built at 2x and displayed at 100% width to stay crisp. The centred `# Logue` heading is gone; the wordmark carries the name. Screenshots. All taken from the current app: the home shot is the merged Home/Ask surface rather than the old dashboard, and the four existing images are refreshed. Ask Logue, Tasks and the Chrome extension are new, so the features written in below have something to show. Twelve images now total 2.4 MB against five at 2.2 MB before. Features. Restructured into eight sections and brought up to 1.1.0: Home and Ask Logue as one surface; the island running the same agent as the main window; the Chrome extension and the loopback bridge it talks to; the inline assistant and menu bar companion; Tasks split out of the old "Search, Tasks & Discovery"; recording resilience; vault import; the route-by-route Privacy tab. Project Layout gains `Logue/Agent/` and `Logue/CrossApp/`; Install gains the extension.
`legacy_swiftui_aspect_ratio` fires on `aspectRatio(contentMode:)` with a constant content mode. The pre-push hook lints the whole repository, so this one violation on `main` blocked every push regardless of what the branch touched. `scaledToFit()` is the same call with the content mode fixed at `.fit`, so the rendering is unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The README still described the app as of 1.0.1. Nothing from 1.1.0 was in it, and its
header carried the Bitwize wordmark under
alt="Logue"— the product had no mark of itsown on the page at all.
Header
A single composite banner: Bitwize.ai at the left edge, the Logue wordmark at the right,
with a
<picture>swap to white silhouettes on dark.The obvious markup for this does not work. GitHub's stylesheet sets
display: block; width: max-contenton markdown tables, which overrideswidth="100%"and collapses percentage-width cells, so a two-cell table renders both logos shrink-wrapped
at the left rather than justified.
styleattributes are stripped, so there is no CSSescape either. Compositing puts the justification in the image's own geometry, so it holds
at every viewport width and renders the same outside GitHub — npm, mirrors, editor previews.
The banner is built at 2x (1800×140) and displayed at
width="100%"to stay crisp atGitHub's content width. The Logue marks are rendered from the app's own
Logue/Resources/LogueLogo*.svg, so they cannot drift from what ships.The centred
# Logueheading is gone — the wordmark carries the name, and GitHub alreadyprints the repository name above the README.
Trade-off: the banner is one link rather than two independently clickable logos, and it
needs recompositing if either mark changes. A three-cell table with a fixed-width transparent
spacer would keep both links, but its width is in pixels, so it puts a horizontal scrollbar
on the header in a narrow window.
Screenshots
All taken from the current app. The home shot is the merged Home/Ask surface rather than the
old dashboard, and the four existing images are refreshed. Ask Logue, Tasks and the Chrome
extension are new, so the features written in below have something to show.
Twelve images now total 2.4 MB, against five at 2.2 MB before — PNG8 without dithering, which
UI screenshots quantise into cleanly.
Features
Restructured into eight sections and brought up to 1.1.0:
Project Layout gains
Logue/Agent/andLogue/CrossApp/; Install gains the extension.Two things worth a look in review
.gitignorewas dropping new README artwork silently. It excludesdocs/*and re-admitsnamed entries, and
docs/images/was never among them. The images the README already renderedwere tracked from before that rule, so nothing looked wrong — but every new file added there
was invisible to git and would have landed on
mainas a broken image link. Now re-admittedalongside
docs/specs/.One unrelated Swift line.
CommandCenterChatView+Composer.swift:16had alegacy_swiftui_aspect_ratioviolation already onmain. The pre-push hook lints the wholerepository, so it blocked every push regardless of what the branch touched.
scaledToFit()isthe same call with the content mode fixed at
.fit, so rendering is unchanged. It is a separatecommit if you would rather it went in on its own.